Systems and methods for providing ip carrier peering

ABSTRACT

Methods and apparatus to achieve internetwork connectivity. Initiation is detected, by a first device on a first network, of an internet protocol (IP) connection with a second device on a second network, wherein the first network includes a plurality of egress devices that are configured to send requests for inter-network connection information. A subset of the egress devices are selected, wherein each of the subset of egress devices are configured to query for connection information relating to the second network. The subset of devices are caused to query the at least one other network for the connection information relating to the second network. The connection information is received relating to the second network. The connection information is caused to be used in establishing the IP connection between the first device and the second device.

CROSS-REFERENCE TO RELATED APPLICATION

This Application claims priority to, and is a continuation of U.S.patent application Ser. No. 15/222,337, filed Jul. 28, 2016. U.S. patentapplication Ser. No. 15/222,337 is incorporated herein by reference inits entirety.

TECHNICAL FIELD

The technical field relates generally to communication networks and moreparticularly to Internet Protocol (IP) connections between IP carriers.

BACKGROUND

A large number of connection between devices, such as telephone calls,are now being carried via packet-switched networks. IP networks haveevolved to allow users to send voice and data, including telephonecalls, through packet-switched networks, such as the Internet, insteadof through older networks like the PSTN. Accordingly, networks oftenutilize the Internet Protocol (IP), which is the basic transmissionprotocol used for Internet communications, to form these connections.For carriers to provide service to subscribers by using IP networks,however, it is necessary for networks to interconnect so that theirsubscribers can connect to each other.

Providing such interconnection generally involves a mechanism by whichcalls that are intended for disparate networks are sent through egressrouting nodes of one network to gateway nodes of other networks. To theextent that one of the available networks recognizes that thedestination device resides on it, the network will take steps to routethe call to the destination device.

A problem exists, however, in that the neither the originating networknor the recipient network have insight into the eventual call path. Whenthe originating network detects initiation of call intended for a deviceon another network, it does not necessarily know the identity or therouting information of the recipient device. Accordingly, it must sendcall information to available networks and rely on the intendedrecipient network to take steps to complete the call. Similarly, therecipient network has no idea when or if a particular call initiated onanother network will be intended for it. Accordingly, it must “listen”for all calls initiated by all available networks to insure that it doesnot miss a call that may be intended for a subscriber. This approach iscostly because it expends system resources on the originating side bysending call requests to available networks regardless of whether allsuch networks are actually recipients and expends resources on therecipient side by requiring the monitoring of call requests by networksthat are not intended recipients. Therefore, what is needed is anapproach for efficient use of system resources while providing IPcarrier interconnection.

SUMMARY

The disclosed systems, methods, and apparatuses that allow for efficientrouting of IP based communications and connections between networks.

The present disclosure is directed at a method. In one embodiment,initiation is detected, by a first device on a first network, of aninternet protocol (IP) connection with a second device on a secondnetwork, wherein the first network includes a plurality of egressdevices that are configured to send requests for inter-networkconnection information. A subset of the egress devices are selected,wherein each of the subset of egress devices are configured to query forconnection information relating to the second network. The subset ofdevices are caused to query the at least one other network for theconnection information relating to the second network. The connectioninformation is received relating to the second network. The connectioninformation is caused to be used in establishing the IP connectionbetween the first device and the second device.

The present disclosure is directed to an apparatus. In one embodiment,the apparatus may include a processor, and memory storing instructionsthat cause the processor to effectuate operations. The operations mayinclude detecting initiation by a first device on a first network of aninternet protocol (IP) connection with a second device on a secondnetwork, wherein the first network includes a plurality of egressdevices that are configured to send requests for inter-networkconnection information; selecting a subset of the egress devices,wherein each of the subset of egress devices are configured to query forconnection information relating to the second network; causing thesubset of devices to query the at least one other network for theconnection information relating to the second network; receiving theconnection information relating to the second network; and causing theconnection information to be used in establishing the IP connectionbetween the first device and the second device.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the herein described systems and methods are described morefully with reference to the accompanying drawings, which provideexamples. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide anunderstanding of the variations in implementing the disclosedtechnology. However, the instant disclosure may take many differentforms and should not be construed as limited to the examples set forthherein. Where practical, like numbers refer to like elements throughout.

FIG. 1 depicts a system and method for intercarrier routing of IPnetwork connections through employment of the principles describedherein.

FIG. 2 depicts one example of a core architecture employable in thesystem of FIG. 1

FIG. 3 is a schematic of an exemplary network device.

FIG. 4 depicts an exemplary communication system that provides wirelesstelecommunication services over wireless communication networks.

FIG. 5 depicts an exemplary communication system that provides wirelesstelecommunication services over wireless communication networks.

FIG. 6 is a diagram of an exemplary telecommunications system in whichthe disclosed methods and processes may be implemented.

FIG. 7 is an example system diagram of a radio access network and a corenetwork.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a general packet radioservice (GPRS) network.

FIG. 9 illustrates an exemplary architecture of a GPRS network.

FIG. 10 is a block diagram of an exemplary public land mobile network(PLMN).

DETAILED DESCRIPTION

Referring to FIG. 1, a system 100 is shown that includes at least oninstance of a device 1 operating on a first network 101, at least oneinstance of a device 2 operating on a second network 102, and a thirdnetwork 103 interconnecting the first network 101 and the second network102. In one example, first network 101 represents a network operated bya first carrier of IP based telecommunication services and secondnetwork 102 represents a network operated by a second carrier of IPbased telecommunication services. Third network 103 in one example is anIP exchange (IPX) network. An IPX network in one example is generally anetwork operated by a plurality of network carriers to provide forinter-network exchange of data between carriers.

It should be noted that the depiction in FIG. 1 is provided forillustrative purposes only and not to limit the disclosure to theembodiment shown therein. The principles described herein are scalableto a greater or lesser number of networks and carriers than what areshown in FIG. 1. Further, at least one instance of first network device1 and at least one instance of second network device 2 are shown todescribe illustrative operations, but many such devices may be operatingthroughout the networks comprising system 100.

Referring further to FIG. 1, first network device 1 and second networkdevice 2 in one example are telecommunications devices that engage innetwork telecommunications to exchange data. Examples of such devicesinclude network device 300 (FIG. 3) and UE 414 (FIG. 4). Such devicesmay also be referred to herein as subscribers, terminals or endpoints.Such devices will at times be initiating or originating devices and attimes be recipient or terminating devices. For illustrative purposesonly, first device 1 will be described as an originating device andsecond device 2 will be described as a recipient device. It should beunderstood, however, that their roles may be reversed.

Similarly, first network 101 will be described in greater detail thansecond network 102 and third network 103. However, the hardware,software, architecture, and functionality of first network 101 areapplicable to second network 102 and third network 103. Finally, forbrevity, an exhaustive network diagram has not been provided for each ofthe networks 101, 102, 103, but it should be understood that thedepiction of networks 101, 102, and 103 represent the hardware,software, architecture, and functionality of telecommunications networksknown to those in the art. Finally, the block diagrams shown herein arefor illustrative purposes only. Accordingly, certain functionality isshown as standalone whereas other functionality is combined. It shouldbe understood that components shown in the figures and described hereinmay be combined or divided as part of a distributed processingenvironment. Exemplary hardware and network configurations applicable tosystem and the component therein is described in connection with FIGS.3-10.

Referring further to FIG. 1, first network 101, second network 102, andthird network 103 in one embodiment comprise a portion of an ElectronicNumber Mapping (ENUM) system infrastructure. ENUM is a suite ofprotocols and architecture designed by the Internet Engineering taskforce unify the E.164 telephone numbering system with the IP addressingsystem. The present disclosure will not provide an in-depth descriptionof the ENUM standard, but will focus on those portions needed todescribe the principles set forth herein. Nevertheless, an exemplarydescription of ENUM terminology, protocols, and infrastructure can befound in U.S. Pat. No. 8,792,481, entitled “Methods, systems, andcomputer program products for providing inter-carrier IP-basedconnections using a common telephone number mapping architecture”, whichis hereby incorporated by reference in its entirety.

One characteristic of ENUM is a hierarchy of databases that are used bynetworks to identify routing information to establish connectionsbetween the various devices that are residing thereon. A multiple-tiereddatabase structure is used to provide carriers with the ability to formconnections between various devices without necessarily sharing networkarchitecture and routing information.

Carriers using ENUM have access to an indirect lookup method to obtainNaming Authority Pointer Resource (NAPTR) records associated withvarious devices residing on other networks. A NAPTR record is receivedfrom a network-based Domain Name Server (DNS) database and is indexed onthe E.164 telephone number of a device. A NAPTR record includes, amongother things, information that designates how and where a device can becontacted. For example, a NAPTR record may designate what types ofcommunications a device can establish, such as a VoIP connection usingSession Initiation Protocol (SIP), a voice connection using the E.164telephone number, a short message service (SMS) or multimedia messageservice (MMS) session, etc. The NAPTR may provide a uniform resourceidentifier (URI) that identifies how to contact the terminal to use aselected service, and may designate a priority for each of the variousconnection methods. ENUM infrastructure includes a plurality of tiereddatabases that are utilized to locate subscriber devices on the variousnetworks making up the infrastructure. For the purposes of the presentdisclosure, three such databases will now be described.

First, a private ENUM database generally provides routing informationfor subscribers within a single network operated by a particularcommunication service provider. If a request is received from anoriginating device on a network to call a device having a particularnumber, the network will first check the private ENUM database. If thenumber resides in the private ENUM database, then the recipient devicealso resides on the network and the two devices may be connected. If theprivate ENUM database does not have a record for the number, then it isunderstood that the recipient device resides on an external network.Accordingly, the originating network needs a mechanism to determine onwhat network the recipient device resides and how to connect with therecipient device. Tier 1 and Tier 2 ENUM databases are used for thispurpose. One principle described herein deviates from this generalapproach.

A Tier 1 ENUM database in one example may provide name server (NS)records that provide routing information that is known to the Tier 1database, but is not known to a private ENUM database. For example, aTier 1 database may identify network databases of other networks, whichare known to the Tier 1 database along with ranges of numbers managed bythe these databases. These other databases are referred to as Tier 2databases. Accordingly, a Tier 1 database may provide the name of anetwork and a Tier 2 database that manages a number associated with aparticular device. The originating network may then contact theappropriate Tier 2 database to receive information needed to complete acall.

In one embodiment, a Tier 2 ENUM database may directly process queriesfrom many different communications providers. For example, one networkmay include the functionality to issue queries to Tier 2 ENUM databasesof other networks to obtain routing information for calls addressed toterminals within other networks. The routing information provided by theTier 2 ENUM database may not provide full routing information inresponse to a query. Rather, a Tier 2 ENUM database may only provideinformation sufficient to identify a network entry point or gateway thatcan be used to route a communication to a particular terminal. Thus, aTier 2 ENUM database may provide information that is sufficient to allowanother carrier to route a call to a terminal without providing completerouting information to the other carrier.

Referring now to FIG. 1, an exemplary description of system 100 is nowprovided for illustrative purposes. As noted, particular aspects ofsystem 100 that are needed to describe certain principles of the presentdisclosure are shown for illustrative purposes, and other components ofsystem 100 are included within this disclosure without being shown inthe FIG. 1. System 100 depicts an illustrative embodiment of an ENUMinfrastructure in accordance with the principles described herein. Itshould be noted that although the principles described herein aredirected to a specific ENUM infrastructure, they are also generallyapplicable to various other networks and system infrastructures.

Referring further to FIG. 1, first network 101 in one example includesprivate ENUM database 104, Tier 2 ENUM database 106, IP multimediasystem (IMS) and egress transfer component (ETC) core 108 (referred tofurther herein as IMS/ETC Core 108), access edge session boardercontroller (A-SBC) 112, and interconnected session border controller(I-SBC) 114.

In one embodiment, private ENUM database 104 provides routing datasolely for terminal devices (e.g. device 1) that operate on firstnetwork 101. In one embodiment, private ENUM database 104 may includerouting data for terminal devices that reside on certain other networks.For example, the carriers operating first network 101 and second network102 may partner to create efficient interconnectivity between theirnetworks. Accordingly, private ENUM database 104 may provide routingdata for first network devices 1 and second network devices 2. In oneexample, the routing data for first network devices 1 may include enoughrouting data to effect a connection between two or more first networkdevices 1 operating on first network 101. In one example, the routingdata for second network devices 2 may be sufficient routing data toestablish a connection between a first network device 1 and a secondnetwork device 2. In another example, the routing data for secondnetwork device 2 may provide a pointer or indicator identifying wheresuch data may be found. For instance, private ENUM database 104 mayinclude an entry for a second network device 2 pointing to Tier 1 ENUMdatabase 120 of third network 103 and/or Tier 2 ENUM database 116 ofsecond network 102.

Referring further to FIG. 1, Tier 2 ENUM database 106 provides routingdata for first network devices 1 to establish connections with deviceson other networks, such as second network devices 2. For example, if asecond network device 2 were to initiate a call with first networkdevice 1, Tier 2 ENUM database 106 may provide routing data to secondnetwork 102 to establish a call or connection between the first networkdevice 1 and the second network device 2. In one example, this routingdata may not represent complete routing data, but may provide an addressfor a component for first network device 1 to utilize in connecting withsecond network device 2.

Referring still to FIG. 1, IMS/ETC core 108 comprises the hardwareand/or software components that provide the architectural framework andfunctionality for delivering IP multimedia communications services.IMS/ETC core 108 handles the establishment, maintenance and take-down ofIP communication sessions. Thus, in first network 101, IMS/ETC core 108handles the processing associated with establishing and maintaining IPconnections, as well as the use of routing for non-IP connections. Inaddition, IMS/ETC core 108 includes egress transfer functionality thatis employed to establish internetwork connectivity between deviceoperating on different networks.

Referring now to FIG. 2, an exemplary description of one embodiment ofIMS/ETC core 108 will now be described for illustrative purposes.IMS/ETC Core 108 in one example comprises IMS Core 202 and ETC 204. IMSCore 202 in on example provides the functionality by which call IPconnections are established, maintained, and terminated on firstnetwork. For example, a call between two first network devices 1 may beestablished, maintained, and terminated by IMS Core 202.IN addition, IMScore 202 may process internet calls upon receipt of routing informationfrom the sending and recipient network.

ETC 204 in one example provides ENUM trigger logic 206 and egressrouting component 208. ENUM trigger logic 206 in one embodimentcomprises the functionality and/or rules, which determine the formand/or function of the processing of calls to other networks. Forexample, if a first network device 1 initiates a call to a secondnetwork device 2, IMS Core 202 may not recognize the number of thesecond network device 2 or otherwise realize that the call is for adevice outside the first network 101. IMS Core 202 will pass theprocessing of the call to ENUM trigger logic 206. ENUM trigger logic 206processes the call based on certain criteria, which will be discussedfurther herein.

In one embodiment, ENUM trigger logic 206 processes calls in conjunctionwith egress routing component 208. Egress routing component 208 in oneembodiment comprises a plurality of nodes 210. The nodes 210 areconfigured to communicate with other networks to query for and receiverouting information such that inter-network connections may beestablished. In one example, nodes 210 may be breakout gate controlfunction (BGCF) nodes through which requests may be sent to othernetworks, such as second network 102 and third network 103, for routinginformation. In one embodiment, a subset 212 of nodes 210 may includeegress client 214. Egress client 214 in one embodiment providesfunctionality for node to communicate with other networks in accordancewith one or more protocols.

For example, an egress client 214 may provide functionality forcommunicating with second network 102 or third network 103 in aspecified manner. Therefore, if trigger logic were to receivenotification of a call being initiated between a first network device 1and a second network device 2, then ENUM trigger logic 206 may utilizethe subset 212 of nodes 210 that include egress client 214 to processthe call. This would minimize use of resources because only those nodes210 configured for operation with second network 102 and/or thirdnetwork 103 would be utilized.

In contrast, if a call were to originate from a first network device 1intended for another network (not shown), then ENUM trigger logic 206may invoke all nodes 210 to communicate with all available networks toprocess the call. Such an approach would not minimize resources becausecertain nodes 210 would be used in a non-directed way.

Referring further to FIG. 2, it should be noted that the rules used bytrigger logic 206 to determine the protocol for processing a particularcall may vary. Criteria that may be used include, but are not limitedto, originating call attributes (e.g. calling number, calling location,originating service type), destination call attributes (e.g. callednumber, country code, national number), and other network eligibilitycriteria (e.g. cost, time of day, and priority). For example, triggerlogic 206 may route all calls intended for a particular network ordestination to a subset 212 of nodes 210 with an egress client 214configured to process such calls. In another example, network analyticsmay determine that a high percentage of calls take place between firstnetwork 101 and second network 102 during a particular time of day.Accordingly, trigger logic 206 may route a percentage of all callsduring the time of day to a subset 212 of nodes 210 with an egressclient 214 configured to request and receive routing informationrelating to network 102.

It should be noted that the preceding examples were provided forillustrative purposes. ENUM trigger logic 206 may use other criteria todistribute calls among nodes 210. The decision of which specific nodes210 to include in subset 212 and/or to use for a given call may be basedon various call distribution techniques, including but not limited tosequential, proportional, equal (round robin), and the like.Furthermore, the nodes 210 within subset 212 that are configured withvarious egress clients 214 may change over time. For example, nodes 210may be either manually or automatically allocated and/or removeddepending on demand. Nodes 210 with the egress client 214 may be addedto egress routing component 208 to ensure sufficient ENUM query capacityis available for one or more networks, e.g., during periods of highernetwork call volumes or upon failure or maintenance outages ofpreviously deployed nodes 210. Similarly, unneeded nodes 210, with orwithout an egress client 214, may be removed during periods of lowercall volume or to remove temporarily added capacity. For example,network analytics may be performed and egress client 214 devices may beadded or subtracted depending on whether network traffic exceeds or doesnot exceed a predetermined threshold. In addition, egress clients 214may be selectively added or removed from nodes 210 based on networkanalytics.

Finally, it should be noted that the function of nodes 210 may bedivided. For instance, a BGCF may be separated from the egress client214. For example, there may be a plurality of BGCF devices and aplurality of egress client devices 214. Egress client devices 214 couldthen invoke BGCF devices as needed. Similarly, if trigger logic 206 wereto determine to send general carrier query, trigger logic 206 may bypassegress client devices 214 and invoke BGCF devices as needed.

The methods to convey the topology of egress routing component 208 totrigger logic 206 may include, but are not limited to, directprovisioning of eligible Carrier ENUM Client node IP addresses or use ofFully Qualified Domain Names (fqdns) to identify the eligible CarrierENUM Client nodes 210.

To summarize, ETC 204 in one embodiment comprises logic and/or rulesthat determine whether or not a call from an originating first networkdevice 1 to a recipient device should trigger a query to a Tier 1 and/orTier 2 ENUM database to identify routing information on another network.In one embodiment, if ETC 204 determines that a call should trigger aquery to a Tier 1 and/or Tier 2 database on another network, then ETC204 may select a subset of the egress client nodes 210 that areconfigured to query for connection information relating to the othernetworks. ETC 204 in one embodiment causes the subset of egress devicesto query the at least one other network for the connection informationrelating to the second network. In another embodiment, ETC 204 maydetermine that a general carrier query should be performed for aparticular call in which case all available nodes 210 may be used torequest routing information from all available carriers. ETC 204 in oneembodiment receives the connection information relating to the secondnetwork. In one embodiment, ETC 204 sends the connection information toIMS core 202, which uses the connection information in establishing anIP connection between the first network device 1 and the recipient.

Referring back to FIG. 1, first network 101 in one embodiment includesA-SBC 112 and I-SBC 114, which are session border controllers (SBCs)used to access the first network 101. In general, a SBC is a device thatis used by VoIP providers to control signaling and media streamsinvolved in setting up, conducting and taking down VoIP calls. Thus, anSBC may be placed in the VoIP signaling path between the calling andcalled terminals. In addition to call setup and takedown, an SBC canprovide, among other things, access control, and data conversionservices for the calls they control. In some cases, an SBC can act as auser agent for a terminal within its network, which allows a network toexercise additional control over calls within the network.

Referring further to FIG. 1, second network 102 is shown as including aTier 2 ENUM database 116 and a SBC 118. It should be understood,however, that second network 102 would also include components that arenot shown, such as other SBCs, ENUM databases, and IMS cores. Tier 2ENUM database 116 provides routing information for devices residing onsecond network 102 that may be used to establish calls with devices onother networks. SBC 118 is used by second network 102 to set up,control, and take down calls for devices on second network 102.

Referring further to FIG. 1, third network 103 in one embodimentincludes a Tier 1 ENUM database 120, SBCs 122, 124, and DNS 126. Tier 1ENUM database 120 in one embodiment provides routing data for Tier 2ENUM databases of networks connected to third network 103 (e.g. network101 and network 102). SBCs 122, 124 provide access to third network 103,and DNS 103 provides a domain name server that includes informationrelating to Tier 2 ENUM databases identified in Tier 1 ENUM database120.

Referring now to FIG. 1, an exemplary description of a method ofoperation of system 100 will now be provided for illustrative purposes.In one embodiment first network device 1 accesses first network 101through A-SBC 112 and initiates a call 151 by inputting a E.164 number.IMS/ETC Core 108 sends a query 153 to private ENUM 104 for the calledE.164. Private ENUM 104 sends a response 155 to ETC 110.

In one example, if the call were for another first network device 1, theresponse 155 may include the routing data for device 1 to be connectedto the other first network device 101. IMS/ETC Core could then completethe call between the two first network devices 1.

In another example, the call may be intended for a second network device2. Accordingly, the response 155 may include a pointer or some otherindicator that second network device 2 resides on second network 102. Inanother example, private ENUM 104 may have records identifying thatrouting information for second network devices can be found on Tier 1ENUM 120 of third network. Such a response 155 may indicate call shouldbe routed accordingly.

Accordingly the response 155 may indicate that the second network device2 resides on the second network 104. Trigger logic 206 of IMS/ETC Core108 would then in accordance to its rules select subset 212 of nodes 210to forward an ENUM query 157. In one embodiment, the ENUM query 157would be populated with information such that the query 157 would bypassthe private ENUM 104 and go to Tier 1 ENUM 120 of third network 103. TheTier 1 ENUM 120 sends a response 159. In one embodiment, the response159 includes the NS records of Tier 2 ENUM 116 of the second network102. IMS/ETC Core 110 would then send a request 161 for DNS 126 toprovide it with destination information for the Tier 2 ENUM 116. DNS 126would resolve the Tier 2 ENUM 116 of the second network 102 and send aresponse 163 to IMS/ETC Core 108. IMS/ETC Core 108 sends a query 165 toTier 2 ENUM 116. The Tier 2 ENUM 116 identifies the entry for device 2and sends a response 167. In one embodiment, the response 167 includesan NAPTR with SBC 118 through which second network 102 wants to acceptcalls from first network. IMS/ETC Core 108 routes the call 151 throughI-SBC 114 to SBC 122 of third network 103. Third network in responseroutes call 151 through SBC 124 to SBC 118 of second network and todevice 2.

Referring to FIG. 1, another example of intercarrier connectivity isdescribed for illustrative purposes. Certain carriers may elect to formthird network 103 as an IPX network to facilitate inter-networkconnectivity between their subscribers. Third network 103 would hostTier 1 ENUM 120, which would include NS record of the Tier 2 ENUM 116 ofparticipating networks, including second network 102. E.164 callinginformation may be stored in first network's private ENUM 104 as a newdomain, e.g., ipx.xyz.net instead of one.xyz.net. Upon initiation of acall to a second network device 102, the private ENUM 104 response 155would include the domain “ipx.xyz.net. IMS/ETC Core 108 may resolvesipx.xyz.net to a subset 212 of nodes 210 with egress client 213 androutes the call to those nodes 210. Nodes 210 will initiate an ENUMquery with e164enum.net to private ENUM 104. The ENUM query will bypassprivate ENUM 104 and reach Tier 1 ENUM 120. Tier 1 ENUM 120 will returnNS records of second network 102 Tier 2 ENUM 116. IMS/ETC Core 108resolve second network Tier 2 ENUM 116 using DNS infrastructure 126 ofthird network. IMS/ETC Core 108 then queries Tier 2 ENUM 116 for routingdata. The Tier 2 ENUM 116 responds with SBC 118 to complete the call.

FIG. 3 is a block diagram of network device 300 that may be connected toor comprise a component of cellular network 112 or wireless network 114.Network device 300 may comprise hardware or a combination of hardwareand software. The functionality to facilitate telecommunications via atelecommunications network may reside in one or combination of networkdevices 300. Network device 300 depicted in FIG. 3 may represent orperform functionality of an appropriate network device 300, orcombination of network devices 300, such as, for example, a component orvarious components of a cellular broadcast system wireless network, aprocessor, a server, a gateway, a node, a mobile switching center (MSC),a short message service center (SMSC), an ALFS, a gateway mobilelocation center (GMLC), a radio access network (RAN), a serving mobilelocation center (SMLC), or the like, or any appropriate combinationthereof. It is emphasized that the block diagram depicted in FIG. 3 isexemplary and not intended to imply a limitation to a specificimplementation or configuration. Thus, network device 300 may beimplemented in a single device or multiple devices (e.g., single serveror multiple servers, single gateway or multiple gateways, singlecontroller or multiple controllers). Multiple network entities may bedistributed or centrally located. Multiple network entities maycommunicate wirelessly, via hard wire, or any appropriate combinationthereof.

Network device 300 may comprise a processor 302 and a memory 304 coupledto processor 302. Memory 304 may contain executable instructions that,when executed by processor 302, cause processor 302 to effectuateoperations associated with mapping wireless signal strength. As evidentfrom the description herein, network device 300 is not to be construedas software per se.

In addition to processor 302 and memory 304, network device 300 mayinclude an input/output system 306. Processor 302, memory 304, andinput/output system 306 may be coupled together (coupling not shown inFIG. 3) to allow communications there between. Each portion of networkdevice 300 may comprise circuitry for performing functions associatedwith each respective portion. Thus, each portion may comprise hardware,or a combination of hardware and software. Accordingly, each portion ofnetwork device 300 is not to be construed as software per se.Input/output system 306 may be capable of receiving or providinginformation from or to a communications device or other network entitiesconfigured for telecommunications. For example, input/output system 306may include a wireless communications (e.g., 3G/4G/GPS) card.Input/output system 306 may be capable of receiving or sending videoinformation, audio information, control information, image information,data, or any combination thereof. Input/output system 306 may be capableof transferring information with network device 300. In variousconfigurations, input/output system 306 may receive or provideinformation via any appropriate means, such as, for example, opticalmeans (e.g., infrared), electromagnetic means (e.g., RF, Wi-Fi,Bluetooth®, ZigBee®), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or a combination thereof.In an example configuration, input/output system 306 may comprise aWi-Fi finder, a two-way GPS chipset or equivalent, or the like, or acombination thereof.

Input/output system 306 of network device 300 also may contain acommunication connection 308 that allows network device 300 tocommunicate with other devices, network entities, or the like.Communication connection 308 may comprise communication media.Communication media typically embody computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, or wireless media such as acoustic, RF,infrared, or other wireless media. The term computer-readable media asused herein includes both storage media and communication media.Input/output system 306 also may include an input device 310 such askeyboard, mouse, pen, voice input device, or touch input device.Input/output system 306 may also include an output device 312, such as adisplay, speakers, or a printer.

Processor 302 may be capable of performing functions associated withtelecommunications, such as functions for processing broadcast messages,as described herein. For example, processor 302 may be capable of, inconjunction with any other portion of network device 300, determining atype of broadcast message and acting according to the broadcast messagetype or content, as described herein.

Memory 304 of network device 300 may comprise a storage medium having aconcrete, tangible, physical structure. As is known, a signal does nothave a concrete, tangible, physical structure. Memory 304, as well asany computer-readable storage medium described herein, is not to beconstrued as a signal. Memory 304, as well as any computer-readablestorage medium described herein, is not to be construed as a transientsignal. Memory 304, as well as any computer-readable storage mediumdescribed herein, is not to be construed as a propagating signal. Memory304, as well as any computer-readable storage medium described herein,is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 304 may include a volatile storage 314 (such as sometypes of RAM), a nonvolatile storage 316 (such as ROM, flash memory), ora combination thereof. Memory 304 may include additional storage (e.g.,a removable storage 318 or a nonremovable storage 320) including, forexample, tape, flash memory, smart cards, CD-ROM, DVD, or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, USB-compatible memory, or any othermedium that can be used to store information and that can be accessed bynetwork device 300. Memory 304 may comprise executable instructionsthat, when executed by processor 302, cause processor 302 to effectuateoperations to map signal strengths in an area of interest.

FIG. 4 illustrates a functional block diagram depicting one example ofan LTE-EPS network architecture 400 related to the current disclosure.In particular, the network architecture 400 disclosed herein is referredto as a modified LTE-EPS architecture 400 to distinguish it from atraditional LTE-EPS architecture.

An example modified LTE-EPS architecture 400 is based at least in parton standards developed by the 3rd Generation Partnership Project (3GPP),with information available at www.3gpp.org. In one embodiment, theLTE-EPS network architecture 400 includes an access network 402, a corenetwork 404, e.g., an EPC or Common BackBone (CBB) and one or moreexternal networks 406, sometimes referred to as PDN or peer entities.Different external networks 406 can be distinguished from each other bya respective network identifier, e.g., a label according to DNS namingconventions describing an access point to the PDN. Such labels can bereferred to as Access Point Names (APN). External networks 406 caninclude one or more trusted and non-trusted external networks such as aninternet protocol (IP) network 408, an IP multimedia subsystem (IMS)network 410, and other networks 412, such as a service network, acorporate network, or the like.

Access network 402 can include an LTE network architecture sometimesreferred to as Evolved Universal mobile Telecommunication systemTerrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial RadioAccess Network (E-UTRAN). Broadly, access network 402 can include one ormore communication devices, commonly referred to as UE 414, and one ormore wireless access nodes, or base stations 416 a, 416 b. Duringnetwork operations, at least one base station 416 communicates directlywith UE 414. Base station 416 can be an evolved Node B (e-NodeB), withwhich UE 414 communicates over the air and wirelessly. UEs 414 caninclude, without limitation, wireless devices, e.g., satellitecommunication systems, portable digital assistants (PDAs), laptopcomputers, tablet devices and other mobile devices (e.g., cellulartelephones, smart appliances, and so on). UEs 414 can connect to eNBs416 when UE 414 is within range according to a corresponding wirelesscommunication technology.

UE 414 generally runs one or more applications that engage in a transferof packets between UE 414 and one or more external networks 406. Suchpacket transfers can include one of downlink packet transfers fromexternal network 406 to UE 414, uplink packet transfers from UE 414 toexternal network 406 or combinations of uplink and downlink packettransfers. Applications can include, without limitation, web browsing,VoIP, streaming media and the like. Each application can pose differentQuality of Service (QoS) requirements on a respective packet transfer.Different packet transfers can be served by different bearers withincore network 404, e.g., according to parameters, such as the QoS.

Core network 404 uses a concept of bearers, e.g., EPS bearers, to routepackets, e.g., IP traffic, between a particular gateway in core network404 and UE 414. A bearer refers generally to an IP packet flow with adefined QoS between the particular gateway and UE 414. Access network402, e.g., E UTRAN, and core network 404 together set up and releasebearers as required by the various applications. Bearers can beclassified in at least two different categories: (i) minimum guaranteedbit rate bearers, e.g., for applications, such as VoIP; and (ii)non-guaranteed bit rate bearers that do not require guarantee bit rate,e.g., for applications, such as web browsing.

In one embodiment, the core network 404 includes various networkentities, such as MME 418, SGW 420, Home Subscriber Server (HSS) 422,Policy and Charging Rules Function (PCRF) 424 and PGW 426. In oneembodiment, MME 418 comprises a control node performing a controlsignaling between various equipment and devices in access network 402and core network 404. The protocols running between UE 414 and corenetwork 404 are generally known as Non-Access Stratum (NAS) protocols.

For illustration purposes only, the terms MME 418, SGW 420, HSS 422 andPGW 426, and so on, can be server devices, but may be referred to in thesubject disclosure without the word “server.” It is also understood thatany form of such servers can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as bearer pathsand/or interfaces are terms that can include features, methodologies,and/or fields that may be described in whole or in part by standardsbodies such as the 3GPP. It is further noted that some or allembodiments of the subject disclosure may in whole or in part modify,supplement, or otherwise supersede final or proposed standards publishedand promulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW420 routes and forwards all user data packets. SGW 420 also acts as amobility anchor for user plane operation during handovers between basestations, e.g., during a handover from first eNB 416 a to second eNB 416b as may be the result of UE 414 moving from one area of coverage, e.g.,cell, to another. SGW 420 can also terminate a downlink data path, e.g.,from external network 406 to UE 414 in an idle state, and trigger apaging operation when downlink data arrives for UE 414. SGW 420 can alsobe configured to manage and store a context for UE 414, e.g., includingone or more of parameters of the IP bearer service and network internalrouting information. In addition, SGW 420 can perform administrativefunctions, e.g., in a visited network, such as collecting informationfor charging (e.g., the volume of data sent to or received from theuser), and/or replicate user traffic, e.g., to support a lawfulinterception. SGW 420 also serves as the mobility anchor forinterworking with other 3GPP technologies such as universal mobiletelecommunication system (UMTS).

At any given time, UE 414 is generally in one of three different states:detached, idle, or active. The detached state is typically a transitorystate in which UE 414 is powered on but is engaged in a process ofsearching and registering with network 402. In the active state, UE 414is registered with access network 402 and has established a wirelessconnection, e.g., radio resource control (RRC) connection, with eNB 416.Whether UE 414 is in an active state can depend on the state of a packetdata session, and whether there is an active packet data session. In theidle state, UE 414 is generally in a power conservation state in whichUE 414 typically does not communicate packets. When UE 414 is idle, SGW420 can terminate a downlink data path, e.g., from one peer entity 406,and triggers paging of UE 414 when data arrives for UE 414. If UE 414responds to the page, SGW 420 can forward the IP packet to eNB 416 a.

HSS 422 can manage subscription-related information for a user of UE414. For example, tHSS 422 can store information such as authorizationof the user, security requirements for the user, quality of service(QoS) requirements for the user, etc. HSS 422 can also hold informationabout external networks 406 to which the user can connect, e.g., in theform of an APN of external networks 406. For example, MME 418 cancommunicate with HSS 422 to determine if UE 414 is authorized toestablish a call, e.g., a voice over IP (VoIP) call before the call isestablished.

PCRF 424 can perform QoS management functions and policy control. PCRF424 is responsible for policy control decision-making, as well as forcontrolling the flow-based charging functionalities in a policy controlenforcement function (PCEF), which resides in PGW 426. PCRF 424 providesthe QoS authorization, e.g., QoS class identifier and bit rates thatdecide how a certain data flow will be treated in the PCEF and ensuresthat this is in accordance with the user's subscription profile.

PGW 426 can provide connectivity between the UE 414 and one or more ofthe external networks 406. In illustrative network architecture 400, PGW426 can be responsible for IP address allocation for UE 414, as well asone or more of QoS enforcement and flow-based charging, e.g., accordingto rules from the PCRF 424. PGW 426 is also typically responsible forfiltering downlink user IP packets into the different QoS-based bearers.In at least some embodiments, such filtering can be performed based ontraffic flow templates. PGW 426 can also perform QoS enforcement, e.g.,for guaranteed bit rate bearers. PGW 426 also serves as a mobilityanchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 402 and core network 404 there may be variousbearer paths/interfaces, e.g., represented by solid lines 428 and 430.Some of the bearer paths can be referred to by a specific label. Forexample, solid line 428 can be considered an S1-U bearer and solid line432 can be considered an S5/S8 bearer according to LTE-EPS architecturestandards. Without limitation, reference to various interfaces, such asS1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 404 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfacesrepresented by dashed lines 430, 434, 436, and 438. Some of thesignaling bearer paths may be referred to by a specific label. Forexample, dashed line 430 can be considered as an S1-MME signalingbearer, dashed line 434 can be considered as an S11 signaling bearer anddashed line 436 can be considered as an S6a signaling bearer, e.g.,according to LTE-EPS architecture standards. The above bearer paths andsignaling bearer paths are only illustrated as examples and it should benoted that additional bearer paths and signaling bearer paths may existthat are not illustrated.

Also shown is a novel user plane path/interface, referred to as theS1-U+ interface 466. In the illustrative example, the S1-U+ user planeinterface extends between the eNB 416 a and PGW 426. Notably, S1-U+path/interface does not include SGW 420, a node that is otherwiseinstrumental in configuring and/or managing packet forwarding betweeneNB 416 a and one or more external networks 406 by way of PGW 426. Asdisclosed herein, the S1-U+ path/interface facilitates autonomouslearning of peer transport layer addresses by one or more of the networknodes to facilitate a self-configuring of the packet forwarding path. Inparticular, such self-configuring can be accomplished during handoversin most scenarios so as to reduce any extra signaling load on the S/PGWs420, 426 due to excessive handover events.

In some embodiments, PGW 426 is coupled to storage device 440, shown inphantom. Storage device 440 can be integral to one of the network nodes,such as PGW 426, for example, in the form of internal memory and/or diskdrive. It is understood that storage device 440 can include registerssuitable for storing address values. Alternatively or in addition,storage device 440 can be separate from PGW 426, for example, as anexternal hard drive, a flash drive, and/or network storage.

Storage device 440 selectively stores one or more values relevant to theforwarding of packet data. For example, storage device 440 can storeidentities and/or addresses of network entities, such as any of networknodes 418, 420, 422, 424, and 426, eNBs 416 and/or UE 414. In theillustrative example, storage device 440 includes a first storagelocation 442 and a second storage location 444. First storage location442 can be dedicated to storing a Currently Used Downlink address value442. Likewise, second storage location 444 can be dedicated to storing aDefault Downlink Forwarding address value 444. PGW 426 can read and/orwrite values into either of storage locations 442, 444, for example,managing Currently Used Downlink Forwarding address value 442 andDefault Downlink Forwarding address value 444 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for eachEPS bearer is the SGW S5-U address for each EPS Bearer. The CurrentlyUsed Downlink Forwarding address” for each EPS bearer in PGW 426 can beset every time when PGW 426 receives an uplink packet, e.g., a GTP-Uuplink packet, with a new source address for a corresponding EPS bearer.When UE 414 is in an idle state, the “Current Used Downlink Forwardingaddress” field for each EPS bearer of UE 414 can be set to a “null” orother suitable value.

In some embodiments, the Default Downlink Forwarding address is onlyupdated when PGW 426 receives a new SGW S5-U address in a predeterminedmessage or messages. For example, the Default Downlink Forwardingaddress is only updated when PGW 426 receives one of a Create SessionRequest, Modify Bearer Request and Create Bearer Response messages fromSGW 420.

As values 442, 444 can be maintained and otherwise manipulated on a perbearer basis, it is understood that the storage locations can take theform of tables, spreadsheets, lists, and/or other data structuresgenerally well understood and suitable for maintaining and/or otherwisemanipulate forwarding addresses on a per bearer basis.

It should be noted that access network 402 and core network 404 areillustrated in a simplified block diagram in FIG. 4. In other words,either or both of access network 402 and the core network 404 caninclude additional network elements that are not shown, such as variousrouters, switches and controllers. In addition, although FIG. 4illustrates only a single one of each of the various network elements,it should be noted that access network 402 and core network 404 caninclude any number of the various network elements. For example, corenetwork 404 can include a pool (i.e., more than one) of MMEs 418, SGWs420 or PGWs 426.

In the illustrative example, data traversing a network path between UE414, eNB 416 a, SGW 420, PGW 426 and external network 406 may beconsidered to constitute data transferred according to an end-to-end IPservice. However, for the present disclosure, to properly performestablishment management in LTE-EPS network architecture 400, the corenetwork, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up requestbetween any two elements within LTE-EPS network architecture 400. Theconnection set up request may be for user data or for signaling. Afailed establishment may be defined as a connection set up request thatwas unsuccessful. A successful establishment may be defined as aconnection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion(e.g., a data radio bearer 446) between UE 414 and eNB 416 a, a secondportion (e.g., an S1 data bearer 428) between eNB 416 a and SGW 420, anda third portion (e.g., an S5/S8 bearer 432) between SGW 420 and PGW 426.Various signaling bearer portions are also illustrated in FIG. 4. Forexample, a first signaling portion (e.g., a signaling radio bearer 448)between UE 414 and eNB 416 a, and a second signaling portion (e.g., S1signaling bearer 430) between eNB 416 a and MME 418.

In at least some embodiments, the data bearer can include tunneling,e.g., IP tunneling, by which data packets can be forwarded in anencapsulated manner, between tunnel endpoints. Tunnels, or tunnelconnections can be identified in one or more nodes of network 400, e.g.,by one or more of tunnel endpoint identifiers, an IP address and a userdatagram protocol port number. Within a particular tunnel connection,payloads, e.g., packet data, which may or may not include protocolrelated information, are forwarded between tunnel endpoints.

An example of first tunnel solution 450 includes a first tunnel 452 abetween two tunnel endpoints 454 a and 456 a, and a second tunnel 452 bbetween two tunnel endpoints 454 b and 456 b. In the illustrativeexample, first tunnel 452 a is established between eNB 416 a and SGW420. Accordingly, first tunnel 452 a includes a first tunnel endpoint454 a corresponding to an S1-U address of eNB 416 a (referred to hereinas the eNB S1-U address), and second tunnel endpoint 456 a correspondingto an S1-U address of SGW 420 (referred to herein as the SGW S1-Uaddress). Likewise, second tunnel 452 b includes first tunnel endpoint454 b corresponding to an S5-U address of SGW 420 (referred to herein asthe SGW S5-U address), and second tunnel endpoint 456 b corresponding toan S5-U address of PGW 426 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 450 is referred toas a two tunnel solution, e.g., according to the GPRS Tunneling ProtocolUser Plane (GTPv1-U based), as described in 3GPP specification TS29.281, incorporated herein in its entirety. It is understood that oneor more tunnels are permitted between each set of tunnel end points. Forexample, each subscriber can have one or more tunnels, e.g., one foreach PDP context that they have active, as well as possibly havingseparate tunnels for specific connections with different quality ofservice requirements, and so on.

An example of second tunnel solution 458 includes a single or directtunnel 460 between tunnel endpoints 462 and 464. In the illustrativeexample, direct tunnel 460 is established between eNB 416 a and PGW 426,without subjecting packet transfers to processing related to SGW 420.Accordingly, direct tunnel 460 includes first tunnel endpoint 462corresponding to the eNB S1-U address, and second tunnel endpoint 464corresponding to the PGW S5-U address. Packet data received at eitherend can be encapsulated into a payload and directed to the correspondingaddress of the other end of the tunnel. Such direct tunneling avoidsprocessing, e.g., by SGW 420 that would otherwise relay packets betweenthe same two endpoints, e.g., according to a protocol, such as the GTP-Uprotocol.

In some scenarios, direct tunneling solution 458 can forward user planedata packets between eNB 416 a and PGW 426, by way of SGW 420. That is,SGW 420 can serve a relay function, by relaying packets between twotunnel endpoints 416 a, 426. In other scenarios, direct tunnelingsolution 458 can forward user data packets between eNB 416 a and PGW426, by way of the S1 U+ interface, thereby bypassing SGW 420.

Generally, UE 414 can have one or more bearers at any one time. Thenumber and types of bearers can depend on applications, defaultrequirements, and so on. It is understood that the techniques disclosedherein, including the configuration, management and use of varioustunnel solutions 450, 458, can be applied to the bearers on anindividual bases. That is, if user data packets of one bearer, say abearer associated with a VoIP service of UE 414, then the forwarding ofall packets of that bearer are handled in a similar manner. Continuingwith this example, the same UE 414 can have another bearer associatedwith it through the same eNB 416 a. This other bearer, for example, canbe associated with a relatively low rate data session forwarding userdata packets through core network 404 simultaneously with the firstbearer. Likewise, the user data packets of the other bearer are alsohandled in a similar manner, without necessarily following a forwardingpath or solution of the first bearer. Thus, one of the bearers may beforwarded through direct tunnel 458; whereas, another one of the bearersmay be forwarded through a two-tunnel solution 450.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as processor 302, UE 414, eNB 416, MME 418, SGW420, HSS 422, PCRF 424, PGW 426 and other devices of FIGS. 1, 2, and 4.In some embodiments, the machine may be connected (e.g., using a network502) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine in aserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., acentral processing unit (CPU)), a graphics processing unit (GPU, orboth), a main memory 506 and a static memory 508, which communicate witheach other via a bus 510. The computer system 500 may further include adisplay unit 512 (e.g., a liquid crystal display (LCD), a flat panel, ora solid state display). Computer system 500 may include an input device514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), adisk drive unit 518, a signal generation device 520 (e.g., a speaker orremote control) and a network interface device 522. In distributedenvironments, the embodiments described in the subject disclosure can beadapted to utilize multiple display units 512 controlled by two or morecomputer systems 500. In this configuration, presentations described bythe subject disclosure may in part be shown in a first of display units512, while the remaining portion is presented in a second of displayunits 512.

The disk drive unit 518 may include a tangible computer-readable storagemedium 524 on which is stored one or more sets of instructions (e.g.,software 526) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above.Instructions 526 may also reside, completely or at least partially,within main memory 506, static memory 508, or within processor 504during execution thereof by the computer system 500. Main memory 506 andprocessor 504 also may constitute tangible computer-readable storagemedia.

As shown in FIG. 6, telecommunication system 600 may include wirelesstransmit/receive units (WTRUs) 602, a RAN 604, a core network 606, apublic switched telephone network (PSTN) 608, the Internet 610, or othernetworks 612, though it will be appreciated that the disclosed examplescontemplate any number of WTRUs, base stations, networks, or networkelements. Each WTRU 602 may be any type of device configured to operateor communicate in a wireless environment. For example, a WTRU maycomprise drone 102, a mobile device, network device 300, or the like, orany combination thereof. By way of example, WTRUs 602 may be configuredto transmit or receive wireless signals and may include a UE, a mobilestation, a mobile device, a fixed or mobile subscriber unit, a pager, acellular telephone, a PDA, a smartphone, a laptop, a netbook, a personalcomputer, a wireless sensor, consumer electronics, or the like. WTRUs602 may be configured to transmit or receive wireless signals over anair interface 614.

Telecommunication system 600 may also include one or more base stations616. Each of base stations 616 may be any type of device configured towirelessly interface with at least one of the WTRUs 602 to facilitateaccess to one or more communication networks, such as core network 606,PTSN 608, Internet 610, or other networks 612. By way of example, basestations 616 may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a site controller, an access point(AP), a wireless router, or the like. While base stations 616 are eachdepicted as a single element, it will be appreciated that base stations616 may include any number of interconnected base stations or networkelements.

RAN 604 may include one or more base stations 616, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 616 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 616 may be divided intothree sectors such that base station 616 may include three transceivers:one for each sector of the cell. In another example, base station 616may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 616 may communicate with one or more of WTRUs 602 over airinterface 614, which may be any suitable wireless communication link(e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visiblelight). Air interface 614 may be established using any suitable radioaccess technology (RAT).

More specifically, as noted above, telecommunication system 600 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish air interface 614 using wideband CDMA (WCDMA). WCDMA mayinclude communication protocols, such as High-Speed Packet Access (HSPA)or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink PacketAccess (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected toRAN 604 may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish air interface 614using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 mayimplement radio technologies such as IEEE 602.16 (i.e., WorldwideInteroperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×,CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95(IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSMEvolution (EDGE), GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B, Home eNode B, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 616 and associated WTRUs 602 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 616 and associated WTRUs 602 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 616and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA,CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.As shown in FIG. 6, base station 616 may have a direct connection toInternet 610. Thus, base station 616 may not be required to accessInternet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be anytype of network configured to provide voice, data, applications, and/orvoice over internet protocol (VoIP) services to one or more WTRUs 602.For example, core network 606 may provide call control, billingservices, mobile location-based services, pre-paid calling, Internetconnectivity, video distribution or high-level security functions, suchas user authentication. Although not shown in FIG. 6, it will beappreciated that RAN 604 or core network 606 may be in direct orindirect communication with other RANs that employ the same RAT as RAN604 or a different RAT. For example, in addition to being connected toRAN 604, which may be utilizing an E-UTRA radio technology, core network606 may also be in communication with another RAN (not shown) employinga GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to accessPSTN 608, Internet 610, or other networks 612. PSTN 608 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). For LTE core networks, core network 606 may use IMS core614 to provide access to PSTN 608. Internet 610 may include a globalsystem of interconnected computer networks or devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP), or IP in the TCP/IP internetprotocol suite. Other networks 612 may include wired or wirelesscommunications networks owned or operated by other service providers.For example, other networks 612 may include another core networkconnected to one or more RANs, which may employ the same RAT as RAN 604or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may includemulti-mode capabilities. That is, WTRUs 602 may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, one or more WTRUs 602 may beconfigured to communicate with base station 616, which may employ acellular-based radio technology, and with base station 616, which mayemploy an IEEE 802 radio technology.

FIG. 7 is an example system 400 including RAN 604 and core network 606.As noted above, RAN 604 may employ an E-UTRA radio technology tocommunicate with WTRUs 602 over air interface 614. RAN 604 may also bein communication with core network 606.

RAN 604 may include any number of eNode-Bs 702 while remainingconsistent with the disclosed technology. One or more eNode-Bs 702 mayinclude one or more transceivers for communicating with the WTRUs 602over air interface 614. Optionally, eNode-Bs 702 may implement MIMOtechnology. Thus, one of eNode-Bs 702, for example, may use multipleantennas to transmit wireless signals to, or receive wireless signalsfrom, one of WTRUs 602.

Each of eNode-Bs 702 may be associated with a particular cell (notshown) and may be configured to handle radio resource managementdecisions, handover decisions, scheduling of users in the uplink ordownlink, or the like. As shown in FIG. 7 eNode-Bs 702 may communicatewith one another over an X2 interface.

Core network 606 shown in FIG. 7 may include a mobility managementgateway or entity (MME) 704, a serving gateway 706, or a packet datanetwork (PDN) gateway 708. While each of the foregoing elements aredepicted as part of core network 606, it will be appreciated that anyone of these elements may be owned or operated by an entity other thanthe core network operator.

MME 704 may be connected to each of eNode-Bs 702 in RAN 604 via an S1interface and may serve as a control node. For example, MME 704 may beresponsible for authenticating users of WTRUs 602, bearer activation ordeactivation, selecting a particular serving gateway during an initialattach of WTRUs 602, or the like. MME 704 may also provide a controlplane function for switching between RAN 604 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNode-Bs 702 in RAN 604via the S1 interface. Serving gateway 706 may generally route or forwarduser data packets to or from the WTRUs 602. Serving gateway 706 may alsoperform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink data isavailable for WTRUs 602, managing or storing contexts of WTRUs 602, orthe like.

Serving gateway 706 may also be connected to PDN gateway 708, which mayprovide WTRUs 602 with access to packet-switched networks, such asInternet 610, to facilitate communications between WTRUs 602 andIP-enabled devices.

Core network 606 may facilitate communications with other networks. Forexample, core network 606 may provide WTRUs 602 with access tocircuit-switched networks, such as PSTN 608, such as through IMS core614, to facilitate communications between WTRUs 602 and traditionalland-line communications devices. In addition, core network 606 mayprovide the WTRUs 602 with access to other networks 612, which mayinclude other wired or wireless networks that are owned or operated byother service providers.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network as describedherein. In the example packet-based mobile cellular network environmentshown in FIG. 8, there are a plurality of base station subsystems (BSS)800 (only one is shown), each of which comprises a base stationcontroller (BSC) 802 serving a plurality of BTSs, such as BTSs 804, 806,808. BTSs 804, 806, 808 are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexample fashion, the packet traffic originating from mobile devices istransported via an over-the-air interface to BTS 808, and from BTS 808to BSC 802. Base station subsystems, such as BSS 800, are a part ofinternal frame relay network 810 that can include a service GPRS supportnodes (SGSN), such as SGSN 812 or SGSN 814. Each SGSN 812, 814 isconnected to an internal packet network 816 through which SGSN 812, 814can route data packets to or from a plurality of gateway GPRS supportnodes (GGSN) 818, 820, 822. As illustrated, SGSN 814 and GGSNs 818, 820,822 are part of internal packet network 816. GGSNs 818, 820, 822 mainlyprovide an interface to external IP networks such as PLMN 824, corporateintranets/internets 826, or Fixed-End System (FES) or the publicInternet 828. As illustrated, subscriber corporate network 826 may beconnected to GGSN 820 via a firewall 830. PLMN 824 may be connected toGGSN 820 via a boarder gateway router (BGR) 832. A Remote AuthenticationDial-In User Service (RADIUS) server 834 may be used for callerauthentication when a user calls corporate network 826.

Generally, there may be a several cell sizes in a network, referred toas macro, micro, pico, femto or umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 9 illustrates an architecture of a typical GPRS network 900 asdescribed herein. The architecture depicted in FIG. 9 may be segmentedinto four groups: users 902, RAN 904, core network 906, and interconnectnetwork 908. Users 902 comprise a plurality of end users, who each mayuse one or more devices 910. Note that device 910 is referred to as amobile subscriber (MS) in the description of network shown in FIG. 9. Inan example, device 910 comprises a communications device (e.g., firstnetwork device 1, second network device 2, mobile positioning center116, network device 300, any of detected devices 500, second device 508,access device 604, access device 606, access device 608, access device610 or the like, or any combination thereof). Radio access network 904comprises a plurality of BSSs such as BSS 912, which includes a BTS 914and a BSC 916. Core network 906 may include a host of various networkelements. As illustrated in FIG. 9, core network 906 may comprise MSC918, service control point (SCP) 920, gateway MSC (GMSC) 922, SGSN 924,home location register (HLR) 926, authentication center (AuC) 928,domain name system (DNS) server 930, and GGSN 932. Interconnect network908 may also comprise a host of various networks or other networkelements. As illustrated in FIG. 9, interconnect network 908 comprises aPSTN 934, an FES/Internet 936, a firewall 1038, or a corporate network940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 9, whenMS 910 initiates the attach process by turning on the networkcapabilities of the mobile device, an attach request is sent by MS 910to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 wasattached before, for the identity of MS 910. Upon receiving the identityof MS 910 from the other SGSN, SGSN 924 requests more information fromMS 910. This information is used to authenticate MS 910 together withthe information provided by HLR 926. Once verified, SGSN 924 sends alocation update to HLR 926 indicating the change of location to a newSGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS910 was attached before, to cancel the location process for MS 910. HLR926 then notifies SGSN 924 that the location update has been performed.At this time, SGSN 924 sends an Attach Accept message to MS 910, whichin turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1038, to reach corporatenetwork 940.

FIG. 10 illustrates a PLMN block diagram view of an example architecturethat may be replaced by a telecommunications system. In FIG. 10, solidlines may represent user traffic signals, and dashed lines may representsupport signaling. MS 1002 is the physical equipment used by the PLMNsubscriber. For example, drone 102, network device 300, the like, or anycombination thereof may serve as MS 1002. MS 1002 may be one of, but notlimited to, a cellular telephone, a cellular telephone in combinationwith another electronic device or any other wireless mobilecommunication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1004 is responsible for communicating with MS 1002and may support one or more cells. BSS 1004 is responsible for handlingcellular traffic and signaling between MS 1002 and a core network 1010.Typically, BSS 1004 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012contains a Radio Network Controller (RNC) 1014 and one or more Nodes B1016. RNS 1012 may support one or more cells. RNS 1012 may also includeone or more RNC 1014/Node B 1016 pairs or alternatively a single RNC1014 may manage multiple Nodes B 1016. RNS 1012 is responsible forcommunicating with MS 1002 in its geographically defined area. RNC 1014is responsible for controlling Nodes B 1016 that are connected to it andis a control element in a UMTS radio access network. RNC 1014 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1002 access tocore network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless datacommunications for MS 1002 and UE 1024. E-UTRAN 1018 provides higherdata rates than traditional UMTS. It is part of the LTE upgrade formobile networks, and later releases meet the requirements of theInternational Mobile Telecommunications (IMT) Advanced and are commonlyknown as a 4G networks. E-UTRAN 1018 may include of series of logicalnetwork components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B(eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment(UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 1018. The improved performance of the E-UTRAN1018 relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

Typically MS 1002 may communicate with any or all of BSS 1004, RNS 1012,or E-UTRAN 1018. In a illustrative system, each of BSS 1004, RNS 1012,and E-UTRAN 1018 may provide MS 1002 with access to core network 1010.Core network 1010 may include of a series of devices that route data andcommunications between end users. Core network 1010 may provide networkservice functions to users in the circuit switched (CS) domain or thepacket switched (PS) domain. The CS domain refers to connections inwhich dedicated network resources are allocated at the time ofconnection establishment and then released when the connection isterminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed or handled independently ofall other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network1010, and interacts with VLR/MSC server 1028 and GMSC server 1030 inorder to facilitate core network 1010 resource control in the CS domain.Functions of CS-MGW 1026 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1026 may receiveconnections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order tofacilitate network functionality. SGSN 1032 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1032 may also store location information such as,but not limited to, GGSN address for each GGSN 1034 where an active PDPexists. GGSN 1034 may implement a location register function to storesubscriber data it receives from SGSN 1032 such as subscription orlocation information.

Serving gateway (S-GW) 1036 is an interface, which provides connectivitybetween E-UTRAN 1018 and core network 1010. Functions of S-GW 1036include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1038 uses information gathered from P-GW1036, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1040 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription dataregarding MS 1002 or UE 1024 for handling calls or data sessions.Networks may contain one HSS 1042 or more if additional resources arerequired. Example data stored by HSS 1042 include, but is not limitedto, user identification, numbering or addressing information, securityinformation, or location information. HSS 1042 may also provide call orsession establishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002enters a new network location, it begins a registration procedure. A MSCserver for that location transfers the location information to the VLRfor the area. A VLR and MSC server may be located in the same computingenvironment, as is shown by VLR/MSC server 1028, or alternatively may belocated in separate computing environments. A VLR may contain, but isnot limited to, user information such as the IMSI, the Temporary MobileStation Identity (TMSI), the Local Mobile Station Identity (LMSI), thelast known location of the mobile station, or the SGSN where the mobilestation was previously registered. The MSC server may containinformation such as, but not limited to, procedures for MS 1002registration or procedures for handover of MS 1002 to a differentsection of core network 1010. GMSC server 1030 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. Userequipment may be classified as either “white listed” or “black listed”depending on its status in the network. If MS 1002 is stolen and put touse by an unauthorized user, it may be registered as “black listed” inEIR 1044, preventing its use on the network. A MME 1046 is a controlnode which may track MS 1002 or UE 1024 if the devices are idle.Additional functionality may include the ability of MME 1046 to contactidle MS 1002 or UE 1024 if retransmission of a previous session isrequired.

As described herein, a telecommunications system wherein management andcontrol utilizing a software designed network (SDN) and a simple IP arebased, at least in part, on user equipment, may provide a wirelessmanagement and control framework that enables common wireless managementand control, such as mobility management, radio resource management,QoS, load balancing, etc., across many wireless technologies, e.g. LTE,Wi-Fi, and future 5G access technologies; decoupling the mobilitycontrol from data planes to let them evolve and scale independently;reducing network state maintained in the network based on user equipmenttypes to reduce network cost and allow massive scale; shortening cycletime and improving network upgradability; flexibility in creatingend-to-end services based on types of user equipment and applications,thus improve customer experience; or improving user equipment powerefficiency and battery life—especially for simple M2M devices—throughenhanced wireless management.

While examples of a telecommunications system in which emergency alertscan be processed and managed have been described in connection withvarious computing devices/processors, the underlying concepts may beapplied to any computing device, processor, or system capable offacilitating a telecommunications system. The various techniquesdescribed herein may be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and devices may take the form of program code (i.e.,instructions) embodied in concrete, tangible, storage media having aconcrete, tangible, physical structure. Examples of tangible storagemedia include floppy diskettes, CD-ROMs, DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a signal. Acomputer-readable storage medium is not a transient signal. Further, acomputer-readable storage medium is not a propagating signal. Acomputer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes an device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

While a telecommunications system has been described in connection withthe various examples of the various figures, it is to be understood thatother similar implementations may be used or modifications and additionsmay be made to the described examples of a telecommunications systemwithout deviating therefrom. For example, one skilled in the art willrecognize that a telecommunications system as described in the instantapplication may apply to any environment, whether wired or wireless, andmay be applied to any number of such devices connected via acommunications network and interacting across the network. Therefore, atelecommunications system as described herein should not be limited toany single example, but rather should be construed in breadth and scopein accordance with the appended claims.

What is claimed:
 1. A method comprising: using a subset of a pluralityof egress devices on a first network to establish one or more internetprotocol (IP) connection between devices on a first network and a secondnetwork; measuring traffic between the first network and the secondnetwork; comparing a measurement of the traffic to a predeterminedthreshold; and configuring, based on a difference in the measurement ofthe traffic to the predetermined threshold, the subset by changing anumber of egress devices in the subset.
 2. The method of claim 1,further comprising: determining that a first device is on the firstnetwork and a second device is on the second network; and determining toquery the second network based on information relating to at least oneof the first device, the second device, and network criteria.
 3. Themethod of claim 2, wherein the step of determining that the seconddevice is on the second network comprises: receiving identifyinginformation of the second device; comparing the identifying informationto a private E. 164 Number Mapping (ENUM) database; and determining fromthe comparison that the second device is on the second network.
 4. Themethod of claim 2, wherein the information relating to at least one ofthe first device and the second device comprises at least one of a firstdevice identifier, a first device location, a first device service type,second device identifier, a second device location, and a second devicelocation.
 5. The method of claim 2, wherein the network criteriacomprises at least one of connection cost, time of day, and connectionpriority.
 6. The method of claim 1, wherein the step of configuring thesubset comprises adding egress devices to the subset if the measurementis greater than the predetermined threshold.
 7. The method of claim 1,wherein the step of configuring the subset comprises removing egressdevices from the subset if the measurement is less than thepredetermined threshold.
 8. The method of claim 1, wherein the step ofusing comprises: causing the subset of devices to identify connectioninformation relating to the second network; and causing the connectioninformation to be used in establishing the IP connection between thefirst device and the second device.
 9. The method of claim 8, whereinidentifying connection information comprises: receiving connectioninformation from a third network; and using the connection informationfrom the third network to request connection information from the secondnetwork.
 10. The method of claim 8, wherein the third network is an IPexchange (IPX) network.
 11. An apparatus comprising: a processor; andmemory coupled to the processor, the memory comprising executableinstructions that cause the processor to effectuate operationscomprising: using a subset of a plurality of egress devices on a firstnetwork to establish one or more internet protocol (IP) connectionbetween devices on a first network and a second network; measuringtraffic between the first network and the second network; comparing ameasurement of the traffic to a predetermined threshold; andconfiguring, based on a difference in the measurement of the traffic tothe predetermined threshold, the subset by changing a number of egressdevices in the subset.
 12. The apparatus of claim 11, wherein theoperations further comprise: determining that a first device is on thefirst network and a second device is on the second network; anddetermining to query the second network based on information relating toat least one of the first device, the second device, and networkcriteria.
 13. The apparatus of claim 12, wherein determining that thesecond device is on the second network comprises: receiving identifyinginformation of the second device; comparing the identifying informationto a private E. 164 Number Mapping (ENUM) database; and determining fromthe comparison that the second device is on the second network.
 14. Theapparatus of claim 12, wherein the information relating to at least oneof the first device and the second device comprises at least one of afirst device identifier, a first device location, a first device servicetype, second device identifier, a second device location, and a seconddevice location.
 15. The apparatus of claim 12, wherein the networkcriteria comprises at least one of connection cost, time of day, andconnection priority.
 16. The apparatus of claim 11, wherein configuringcomprises adding egress devices to the subset if the measurement isgreater than the predetermined threshold.
 17. The apparatus of claim 11,wherein configuring comprises removing egress devices from the subset ifthe measurement is less than the predetermined threshold.
 18. Theapparatus of claim 11, wherein using the subset comprises: causing thesubset of devices to identify connection information relating to thesecond network; and causing the connection information to be used inestablishing the IP connection between the first device and the seconddevice.
 19. The apparatus of claim 18, wherein identifying connectioninformation comprises: receiving connection information from a thirdnetwork; and using the connection information from the third network torequest connection information from the second network.
 20. Theapparatus of 18, wherein the operation of detecting initiationcomprises: receiving connection information from a third network; andusing the connection information from the third network to requestconnection information from the second network.